\chapter{Introduction}
	\section{Purpose of the system}
		The purpose of Da CalendarSystem is to give the users of the sytem an easy way to get an overview over their appointments, and let them create, change or delete their appontments in a user friendly way. The users can furthermore share their calendars with other users, for example in case of employees sharing a calendar.
	\section{Design goals}
		\begin{framed}
		\textbf{Design goals for Da CalendarSystem}
		\begin{itemize}
		\item\textbf{Response time:} Da CalendarSystem should always have a response time on less than five seconds for any task [rephrased nonfunctional requirement 5].
		\item\textbf{Reliability:} Data must persist through server crashes [generalization of nonfunctional requirement 2].
		\item\textbf{Security:} Every user of the system must have a UserAccount to be able to access the system. A user must only be able to access their own calendar and calendars other users have shared with them [generalization of nonfunctional requirement 3 and 4].
		\item\textbf{Deployment cost:} There should be no cost of installing the system or training the users since the user should have basic calendar knowledge [inferred from nonfunctional requirement 1].
		\item\textbf{Usability:} Any user with basic calendar and computer knowledge should be able to use Da CalendarSystem without prior use [rephrased nonfunctional requirement 1].
		\end{itemize}
		\end{framed}
	\section{Definitions, acronyms and abbreviations}
	\section{References}
	\section{Overview}